|
|
|
|
|
|
|
Your application needs to be able to roll back a task or flow of work when business conditions require this. This is quite similar to implementing an Undo mechanism for tasks. Rolling back a task can be quite complicated and requires particular attention to details in your sequence diagrams and quite a bit of analysis with users, especially process owners. |
|
|
|
|
|
|
|
|
Process owners and/or application administrators sometimes need to specify the completion time for each task, and possibly each step within a task, in the process. You might design the application to allow the completion time to be fixed, or allowed to vary depending on the weight of the task, the product, the customer, and so on. |
|
|
|
|
|
|
|
|
The Workgroup and User Security Subsystem Object Model |
|
|
|
|
|
|
|
|
The Branch Manager of your client, the Second Bank of Carrollton, calls you to see how things are going with the application. You tell her you're at the point where you're modeling the bank's workgroup and security requirements and thus need her help in verifying any related concerns. She assures you that the workgroup model is very simple as not much work flows from one workgroup to another. After speaking with her database administrator, she gives you the following additional specifications: |
|
|
|
|
|
|
|
|
1. Although I'll sign off on cash deposit record forms for cash deposits in excess of $10,000, I want each record stored in the Regulations database in the tblCash_Deposit_Records table. Each record has a field, WasSigned, that must be assigned a value: True if the customer, the teller, and myself have signed, or False if otherwise. Most of the time, all three signatures are there. But sometimes, I'm not available, so I sign them at some point before the end of the day. Thus, I want a report automatically printed by 3 p.m. daily listing just the account number and the value of the WasSigned field. My printer ID is \bank01\brmgr. Every week, our regional bank compliance officers audit us to make sure the cash deposit records are signed. |
|
|
|
|
|
|
|
|
2. Be sure that, for every new account, the DOS-based check account history system is called so that the teller doesn't have to leave the session in the new application to start another. The DOS-based system is very important to our workflow. |
|
|
|
|
|